Sub-tree .emanoteignore events (e.g. sub/.emanoteignore) carry the
same R.IgnoreFile tag as the layer-root file but configure no
patterns. Skip the disk reload when a batch contains only sub-tree
events; previously the predicate was exported but had no caller.

Closes hickey finding #5 / lowy finding #2.

…noreFileChanges

LuaFilter hot-reload is implemented inside Patch.patchModel; the
.emanoteignore hot-reload runs *upstream* of patchModel, inside
Source.Dynamic. A reader could miss the asymmetry without a pointer
at each end — add explicit cross-references to keep the structure
discoverable.

Closes lowy finding #4.

Matches the codebase convention (ModelT, Note, StaticFile, EmanoteConfig)
of accessing internal record state through optics rather than raw
underscore-prefix selectors.

Closes lowy finding #3.

applyFiltered and reEmitModified both ran their own NE.filter +
length comparison + nonEmpty branch to decide whether to dispatch
Refresh, Refresh-with-trimmed-overlays, or Delete. Lift the pure
decision into 'Emanote.Source.Ignore.classifyOverlays' returning an
'OverlayOutcome' so both call sites read as: classify → branch →
dispatch. The bookkeeping (recordModified/forgetModified) stays at
the call site where it belongs.

Closes hickey finding #4.

…lice

Previously _isPatterns and _isModifiedEvents were two TVars whose
invariants (entry absent from set ↔ visible in model; entry present
↔ suppressed) were held by hand at three sites. Combine them into a
single 'IgnoreSlice' record behind one TVar and route every read
through 'snapshotSlice' / every write through 'updateSlice'. The
single-transaction property gives a future invariant linking the two
fields one place to live, and 'recordModified' / 'forgetModified' now
delegate to the slice helper instead of poking a raw TVar.

Closes hickey finding #3.

applyFiltered, applyOne, handleIgnoreFileChanges, evictNewlyIgnored,
and reEmitModified each threaded the same four invariants positionally
(layers, noteFn, storkIndex, ignoreState). Bundle them into a single
HandlerCtx so a new helper that needs (say) storkIndex alongside the
ignore state doesn't have to grow another positional argument.

Closes hickey finding #6.

evictNewlyIgnored only walked _modelNotes, leaving static files
(images, PDFs, source-code embeds, ...) serving when their path
matched a freshly-added pattern. Add _staticFileSource :: Maybe
(Loc, FilePath) to StaticFile, populate it from the top overlay in
Patch.insertStaticFile, and walk _modelStaticFiles alongside notes
in evictNewlyIgnored.

The hot-reload coverage for YAML data and Heist templates remains a
known limitation — neither carries per-layer source metadata in the
model today. Documented in docs/guide/emanoteignore.md.

Closes hickey finding #2 / lowy finding #1.

…o their guides

The hot-reload caveat for YAML data and Heist templates now points at
[[yaml-config]] and [[html-template]] so a reader following the
limitation has the surrounding context one click away.

evictNewlyIgnored unconditionally overwrote any existing ledger entry
with a single-element ((loc, lfp) :| []) overlay drawn from
_noteSource / _staticFileSource. If a previous OverlayPartial had
stashed the full multi-layer overlay (e.g. [(Layer1, foo.md),
(Layer2, foo.md)]), that history would be silently lost — a
subsequent pattern relaxation would resurrect the file from the
wrong layer in multi-layer setups.

Add 'recordModifiedIfAbsent' and route both note and static-file
eviction through it. The original 'recordModified' (overwrite-wins)
stays the right helper for 'applyFiltered', where the new event from
unionmount carries the freshest overlay.

…leType

The handwritten isMdRoute case-split duplicates the 'HasExt' class's
'fileType' method, which already resolves to the correct
'R.LMLType R.Md' / 'R.LMLType R.Org' per its instance. Route via
'withLmlRoute' so the type-class machinery handles the choice.

snapshotSlice / updateSlice / changeEntries / applyOne / mountedPath
each had a one-line Haddock that restated the identifier name. Per
the codebase convention (default to no comments; keep only non-obvious
why), delete them. The two record-helpers (recordModified vs
recordModifiedIfAbsent) keep shortened comments naming the policy
choice — that's the non-obvious distinction.

…e with pointer

The 14-line comment above the R.IgnoreFile branch in Patch.hs repeated
prose that already lives in the haddock for handleIgnoreFileChanges in
Dynamic.hs. Replace with a 3-line cross-reference; Dynamic.hs is the
single source of truth for the LuaFilter-vs-IgnoreFile asymmetry.

…erns empty

Every fsnotify event during a live-reload session runs through
classifyOverlays. For the common case where no layer has any
per-layer patterns, the NE.filter walk + per-overlay Map lookups are
all no-op work. Add a fast path that returns OverlayKept directly
when the pattern map is empty.

…patterns changed

evictNewlyIgnored and reEmitModified previously walked the full
_modelNotes and _modelStaticFiles on every .emanoteignore edit. For a
10k-note notebook each save was O(N), even though a typical edit
touches only one layer's pattern set.

Diff old vs new patterns per Loc once, then filter every walk by Set
membership before applying the heavier isLayerPathIgnored /
classifyOverlays predicates. Correctness: if a layer's patterns
didn't move, no file in that layer can have flipped sides.

Three step definitions (and one new one from this PR) repeated the
same path.join + mkdirSync({recursive: true}) + writeFileSync trio.
Lift it into support/fixture.ts next to stagedFixtureDir; both
step files reuse it. A future step that writes a new fixture file
gets the right ceremony for free.

…steps

Three step definitions ('URL X contains Y within Ns', 'URL X stops
containing Y within Ns', 'I wait for X to contain Y') used the same
request-inspect-sleep-retry loop. Lift it into tests/support/poll.ts
behind a typed predicate + onTimeout pair so each step shrinks to a
4-line wrapper; the page-DOM 'article body contains … within Ns'
step stays put since it uses Playwright's waitForFunction.

filepattern's '**' matches the empty path, so the master pattern
'**/.*/**' silently matched a root-level dotfile like '.emanoteignore'
(via ** = "", .* = ".emanoteignore", trailing ** = ""). The previous
ignorePatterns list passed this to unionmount as a per-source ignore;
unionmount's fsnotify watcher then filtered every .emanoteignore
modify event before it could reach handleIgnoreFileChanges, breaking
the entire hot-reload pipeline this PR was meant to deliver.

Tighten the pattern to '**/.*/**/*' so the trailing component is
required. Dotfile-directory CONTENTS (.git/HEAD, .vscode/settings.json,
.git/objects/00/abc) still match; root-level standalone dotfiles
(.emanoteignore, .gitignore, .envrc, …) no longer do.

Behavior change: root-level dotfiles that the universal pattern was
incidentally filtering — .gitignore, .envrc, .editorconfig, etc. —
are now exposed as AnyExt static files unless the user adds them to
their own .emanoteignore. Most users have nothing sensitive in those
files; users who do can list them in .emanoteignore.

Verified manually: with this fix the two new hot-reload scenarios in
tests/features/emanoteignore.feature flip the matching note's
visibility in well under the 10-second polling budget.

The hot-reload entry now flags that the universal pattern change to
let .emanoteignore through also stops swallowing other root-level
standalone dotfiles (.gitignore, .envrc, .editorconfig, …). Dotfile
*directories* (.git/, .vscode/) are unchanged.